Skip to content

Expose booster-dev #3856

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
May 10, 2024
Merged

Expose booster-dev #3856

merged 4 commits into from
May 10, 2024

Conversation

geo2a
Copy link
Contributor

@geo2a geo2a commented May 10, 2024

Fixes #3855

Follow-up in K: runtimeverification/k#4335

@geo2a geo2a marked this pull request as ready for review May 10, 2024 08:53
@geo2a geo2a requested a review from goodlyrottenapple May 10, 2024 08:53
@geo2a geo2a merged commit df703fe into master May 10, 2024
7 checks passed
@geo2a geo2a deleted the georgy/flake-expose-booster-dev branch May 10, 2024 10:35
rv-jenkins pushed a commit to runtimeverification/k that referenced this pull request May 22, 2024
~Needs runtimeverification/haskell-backend#3856
~Blocked on
#4319 (review)

@PetarMax wants to experiment with Booster-only simplifications in
Kontrol. To avoid the need for power-users of Kontrol to building the
backend from source, we should expose booster-dev in flake.nix and also
forward it to K's flake, so that it is installed with kup install k.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Expose booster-dev from flake.nix
2 participants